A lightweight, flexible, and high-performance dependency injection and service location library for Dart and Flutter. It's production ready for your Flutter app

State management is a critical aspect of building responsive Flutter apps. We often talk about “State Management Solutions” in Flutter, but we rarely break down the components of state management into their constituent parts. Understanding the different components of state management in Flutter can help you understand why you might choose one state management solution over another and identify the simplest ways to do state management. Breaking these components down shows how all state management solutions are built on the same foundation. They are all variants of one underlying principle. This article discusses the components and gives examples of how they work together.

There are four primary components of state management in Flutter: Builder, Controller, State, and Dependency Manager. Each of these components plays a unique role in managing the state of your application.

The controller manages the application’s state and business logic. It notifies the Builder when the state changes. There are two fundamental types of controllers in the core Flutter API: ChangeNotifier and ValueNotifier. They both implement the Listenable interface, which allows them to notify the Builder when the state changes.

ChangeNotifier is a class that extends the Listenable class and provides the notifyListeners() method to notify the builders when the state changes. You may maintain the state in the controller by adding properties to the class. The ChangeNotifier class is a good choice when you need to maintain the mutable state in the controller.

ValueNotifier also extends the Listenable class and provides the value property that holds the current state value. When the value changes, the ValueNotifier notifies the listeners. The ValueNotifier class is a good choice when you need to maintain the immutable state in the controller.

Cubit and Bloc are both controllers that exist in the flutter_bloc library. They both require you to work with immutable state. Finally, StateNotifier is another controller that requires immutable state.

When we say “state management solution” we are often referring to the controller, but the overall solution may include the other components.

A Builder is a widget that listens to state changes and calls setState when a change occurs. This tells Flutter to rebuild the widget tree. Flutter has three popular builders in the toolkit: StreamBuilder, ValueListenableBuilder, and AnimatedBuilder.

We use StreamBuilder with streams, a sequence of asynchronous events. It listens to the stream and rebuilds the widget when new data is available.

We use AnimatedBuilder with any Listenable controller. AnimatedBuilder listens to changes and rebuilds the widget when the Listenable notifies the builder of a change. The original design was for animations only, but this widget is perfect for other kinds of state management.

ValueListenableBuilder is very similar to AnimatedBuilder, but it takes a ValueListenable as a controller. A good example is ValueNotifier.

Another notable builder outside the core framework is BlocBuilder in the flutter_bloc library. This builder is similar to the earlier builders but only works with a controller that implements the StateStreamable class.

State is the data the app holds in memory that the UI reflects. The controller typically manages this. The State can be anything, from a simple boolean value to a complex data structure. The State can exist in the controller class, or a separate class can hold the state. The State can be mutable or immutable. Immutability is not simple in Dart, and you should carefully consider the choice between mutable and immutable. For a more in-depth discussion of immutable state in Dart, see this article.

A dependency manager is a component that mints or holds onto the controller and its dependencies. It can hold onto the controller as a singleton, an object that is only instantiated once and shared across the entire application. It can also propagate the controller and its dependencies throughout the widget tree or expose them globally. In Flutter, there are several dependency managers, including ioc_container, provider, and get_it, but none of these belong to the core Flutter API.

Importantly, dependency managers allow you to substitute dependencies with test doubles like Mockito. This is a critical feature for testing your application.

ioc_container is a dependency manager that uses Inversion of Control principles to manage dependencies. It provides a container that manages the dependencies and allows for dependency injection. You can expose ioc_container throughout the widget tree as an InheritedWidget with flutter_ioc_container.

provider is a dependency manager that primarily uses InheritedWidget to provide objects to its children. It allows for a hierarchical relationship between the parent and child widgets.

get_it is a dependency manager that uses the service locator pattern to manage dependencies. It provides a global singleton instance that can be used across the entire application.

Flutter gives us a comprehensive set of tools to build our applications. The core building blocks are the widgets, controllers, and builders. Where possible, it is always best to use the building blocks that come with the toolkit. This is because the core building blocks are well-tested, performance-optimized and designed to work together. For example, the ValueListenableBuilder is designed to work with the ValueNotifier controller. If we depend on core classes like Listenable or Stream we maximize the chance that components will work together.

Lastly, but most importantly, adding large 3rd party packages, especially those that depend on further packages, makes your app more opaque and harder to maintain. A rule of thumb that I follow is that I should be able to look at the code in the external package and understand what it is doing. The code should be small enough that I would have a hope of fixing it if I found a bug. You can’t depend on 3rd party libraries to work the way you expect them to work. The author may make future decisions that are not in line with your expectations. That’s why packages that only perform one simple function, and limit themselves to being one of the components I mentioned here are safer to use.

So, use 3rd party packages where necessary to extend the basic building blocks, but check that they do the bare minimum and don’t add too much complexity. When a core Flutter building block does the job, use it.

To summarise, we have the following components:

In this example, I use ChangeNotifier as the controller for state management. It holds the mutable state.

I use ioc_container as the dependency manager because neither Dart nor Flutter have a built-in dependency injection framework.

Finally, I use ListenableFutureBuilder as the builder. It has three key features:

You can use a core Flutter builder, but this means you also need to manage the controller as state yourself.

Add these packages with these commands

This is a simple counter example that demonstrates how all the components interact with each other. This example has no StatefulWidgets and all of the business logic exists in the controller. The builder takes care of the widget rebuilds and the dependency manager takes care of creating the controller. You can read about ListenableFutureBuilder here.

Live demo:

This is what the widget tree looks like while waiting for the controller

This is what it looks like once the controller is ready and the counter has been clicked 3 times

The builder, controller, state, and dependency manager work together to manage the state of your application and provide a responsive user interface. If you use these components effectively, you can build reliable and efficient applications. Take the time to learn and understand these components, and you’ll be on your way to building successful Flutter applications.

Share on: